"A common mistake that people make when trying to design something completely foolproof was to underestimate the ingenuity of complete fools."
--Douglas Adams
|
|
Last update
25-January, 2018
|
Requirements Engineering
Project Assignment
Spring 2019
*liberally lifted, with permission, from Dr. Goldsmith's project assignments
CS 585-616 Project Proposals
The choice of "projects" for CS 585-617 is the following. Note that all projects require a presentation at the end of the semester. All presentations require a practice session in advance (see syllabus). Required proposal information is listed below.
Each student must choose a project type and propose the project's goals, learning objectives, deliverables, and milestones.
The proposal and project and presentation deadlines are on the course schedule.
References to research papers and other sources may include URLs, but
do not expect Dr. Hayes to follow links. They must include the who/what/where/when of the paper. That is, author, title, PUBLICATION VENUE, and date. That information must be in plaintext in the proposal. Do not expect Dr. Hayes to follow a link to look it up. You can use scholar.google.com to find papers, and the cite link to get bibliographic information, but please choose a format that does not include "et al.". You can also use dblp.org for (usually better) bibliographic information. And many professors post their papers on personal websites, or on ResearchGate.net or Academia.edu You can use the latter too to request copies of papers.
Please make sure to look at the discussion of
co-operation on projects and plagiarism.
Software Development Projects
This is an opportunity for you to perform the entire software engineering lifecycle (reqts, design, code, test) on a small scope project that revolves around performing analysis or checking or some other activity on requirements. Your proposal should include a description of the system to be developed as well as planned deliverables and milestones, development methodology, and other relevant information such as the language you intend to use
and how you will demonstrate the success of your development.
Application or Evaluation of a Requirements Engineering Technique
You will list the technique you will be applying or evaluating as well as your planned approach to application and/or evaluation. For empirical evaluations, you must
have a plan that includes: research questions, hypotheses, independent and dependent variables, and threats to validity. Ensure that your proposal discusses how you will show success of your application/evaluation.
Software Review of a Requirements Engineering Tool
You will list the software that you will be reviewing, cite its dominant
requirements engineering theme(s), and outline the review.
Written Survey
Your proposal for a written survey
will list the technical papers you will be surveying
and their commonalities, and outline the survey. Dr. Hayes may
ask for revisions of the outline.
A survey should cover (for undergrads) at least three published sources (five for graduate students) - see sources of technical information below. It
should be organized around ideas, not around papers. Do not submit an annotated
bibliography, and do not simply quote from the papers. Discuss the differences
between the questions answered, and between the answers, as well as the similarities. Speculate on why, in papers with experiments, different test cases were used.
In as much as time permits, Dr. Hayes with look over drafts and give feedback.
Sources of technical information
Your material should come from a reputable and refereed source,
preferably a refereed journal or conference proceedings. Tech reports
and random papers found on the web are not acceptable.
If you do not know whether you are looking at a predatory journal or conference,
try looking it up on Beall's list.
-
When a paper is submitted to a (non-predatory) refereed journal, it is read carefully
for correctness and presentation by two to five experts in the field. It
may be read by these experts in several versions before being accepted
for publication. It takes anywhere from four months to several years
from initial submission to publication.
- When a paper is submitted to a (non-predatory) refereed conference,
it is read for innovation, appropriateness to the conference, and
sometimes for correctness by one to three experts in the field. These referees
do not see the version that actually gets printed until it is published.
It takes anywhere from three to six months
from initial submission to publication.
- The purpose of a tech report is to get a time-stamp on your
work. They are not refereed. They "appear" within days of submission.
- Anyone can post a paper on the web. Many do.
Cooperation
Group projects are encouraged. Graduate students may work in pairs, undergraduates may work in groups larger than two. Students may be encouraged to submit particularly good
projects for publication.
The usual applies: plagiarism, copying, or working together without
crediting each other will be punished to the fullest extent of university
regulations.